API

Human resource APIs

GET human-resources/short-term-absences/{shortTermAbsenceId}

Short-term absence details for the provided identifier

HTTP method GET
URI https://api.rambase.net/human-resources/short-term-absences/{shortTermAbsenceId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {shortTermAbsenceId} Short-term absence identifier
Integer, minimum 100000
Successful HTTP status code 200
API resource identifier 3817, version 3

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.

Format:
1
1

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$showDomainDescriptions Boolean, optional Set to "true" to include domain descriptions for fields using domain values. See the Domain values page for more information. Default value is false.
$lang String, optional Specifies the language used in the response, following the 3-letter ISO-639-1 [lll]
$access_token String, optional After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time.
$db String, optional Set the database/company for the request
$format String, optional Set the format of the response to use for the request. Accepted values are "xml", "html", "jsonstream", "json"
$useMinimumVersion Integer, optional Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information.
$select String, optional Use to define the fields to return in the response. Accepts a comma-separated list of field names. See the Expand and select page for more information.

Read more about filters and sorting on how to use filter parameters and named filters.

Read more about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields. Fields colored in grey is expandable fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
<ShortTermAbsence>
2
     <ShortTermAbsenceId
ShortTermAbsenceId

Short-term absence identifier

>
{Integer}</ShortTermAbsenceId>
3
     <Status
Status

Status of short-term absence

Possible domain values can be found here

>
{Integer}</Status>
4
     <CreatedAt
CreatedAt

Date and time of creation

>
{Datetime}</CreatedAt>
5
     <SignedAt
SignedAt

Time when the signature is placed in

>
{Datetime}</SignedAt>
6
     <Description
Description

Description that exlplains the reason for the short-term absence

>
{String}</Description>
7
     <Employee>
8
          <EmployeeId
EmployeeId

Employee identifier

>
{Integer}</EmployeeId>
9
          <EmployeeLink
EmployeeLink

Employee reference

>
{String}</EmployeeLink>
10
     </Employee>
11
     <Period>
12
          <StartedAt
StartedAt

Start time of the short-term absence

>
{Datetime}</StartedAt>
13
          <EndedAt
EndedAt

End time of the short-term absence

>
{Datetime}</EndedAt>
14
     </Period>
15
     <TimeType>
16
          <TimeTypeId
TimeTypeId

Time type identifier

>
{Integer}</TimeTypeId>
17
          <Category
Category

Category of the time type

Possible domain values can be found here

>
{Integer}</Category>
18
          <Description
Description

Description of the time type

>
{String}</Description>
19
          <TimeTypeLink
TimeTypeLink

Reference to the time type

>
{String}</TimeTypeLink>
20
     </TimeType>
21
     <Appointment>
22
          <Regarding
Regarding

Related entity which initiated the reason for the absence

Possible domain values can be found here

>
{String}</Regarding>
23
          <Type
Type

Type of the appointment

Possible domain values can be found here

>
{String}</Type>
24
          <Time
Time

Time of the appointment

>
{Time}</Time>
25
          <Location
Location

Location of the appointment

>
{String}</Location>
26
     </Appointment>
27
</ShortTermAbsence>
1
{
2
     "shortTermAbsence": {
3
          "shortTermAbsenceId
ShortTermAbsenceId

Short-term absence identifier

":
"{Integer}",
4
          "status
Status

Status of short-term absence

Possible domain values can be found here

":
"{Integer}",
5
          "createdAt
CreatedAt

Date and time of creation

":
"{Datetime}",
6
          "signedAt
SignedAt

Time when the signature is placed in

":
"{Datetime}",
7
          "description
Description

Description that exlplains the reason for the short-term absence

":
"{String}",
8
          "employee": {
9
               "employeeId
EmployeeId

Employee identifier

":
"{Integer}",
10
               "employeeLink
EmployeeLink

Employee reference

":
"{String}"
11
          },
12
          "period": {
13
               "startedAt
StartedAt

Start time of the short-term absence

":
"{Datetime}",
14
               "endedAt
EndedAt

End time of the short-term absence

":
"{Datetime}"
15
          },
16
          "timeType": {
17
               "timeTypeId
TimeTypeId

Time type identifier

":
"{Integer}",
18
               "category
Category

Category of the time type

Possible domain values can be found here

":
"{Integer}",
19
               "description
Description

Description of the time type

":
"{String}",
20
               "timeTypeLink
TimeTypeLink

Reference to the time type

":
"{String}"
21
          },
22
          "appointment": {
23
               "regarding
Regarding

Related entity which initiated the reason for the absence

Possible domain values can be found here

":
"{String}",
24
               "type
Type

Type of the appointment

Possible domain values can be found here

":
"{String}",
25
               "time
Time

Time of the appointment

":
"{Time}",
26
               "location
Location

Location of the appointment

":
"{String}"
27
          }
28
     }
29
}

Possible error codes the response might return:

Error 100136 HTTP 404 Settings and Configuration Values (SCV) with these parameters not found